home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
mmgr134.zip
/
MAILMGR.DOC
< prev
next >
Wrap
Text File
|
1992-05-29
|
104KB
|
2,184 lines
┌───────────────────────────────────────────────────────────────────────┐
│ ▒▒▒▄▄▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▄ ▒▒▄ A QWK-compatible mail door for RBBS-PC │
│ ▒▒█▒▒█▒▒█ ▒▒█▀▒▒█ ▒▒█ ▒▒█ Copyright (C) 1991-92 Morrow & Wilson │ █
│ ▒▒█ ▀▀▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▒▒█ All rights reserved │ █
│ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ │ █
│ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒▄ Version 1.34 - May 29, 1992 │ █
│ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ │ █
│ ▒▒▒▄▄▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▄▄ ▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ ▒▒▒▒▒▒▄ │ █
│ ▒▒█▒▒█▒▒█ ▒▒█▀▒▒█ ▒▒█▒▒█▒▒█ ▒▒█▀▒▒█ ▒▒█▀▀▀▀ ▒▒█▀▀▀▀ ▒▒█▀▒▒█ │ █
│ ▒▒█ ▀▀▒▒█ ▒▒▒▒▒▒█ ▒▒█ ▀▒▒▒█ ▒▒▒▒▒▒█ ▒▒█▒▒▒▄ ▒▒▒▒▒▄ ▒▒▒▒▒█▀ │ █
│ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█▀▀▀ ▒▒█▀▒▒▄ │ █
│ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒█ ▒▒▒▒▒▒█ ▒▒▒▒▒▒▄ ▒▒█ ▒▒█ │ █
│ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ │ █
└───────────────────────────────────────────────────────────────────────┘ █
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
TABLE OF CONTENTS
Introduction . . . . . . . . . . . . . . . . . . . . . . . 1
Warranty, distribution, & registration (or lack thereof) . 2
Features & limitations . . . . . . . . . . . . . . . . . . 3
Checklist of requirements . . . . . . . . . . . . . . . . 5
* Before you begin, READ THIS! * . . . . . . . . . . . . . 6
Upgrading from a previous version . . . . . . . . . . . . 7
Installing Mail Manager from scratch . . . . . . . . . . . 9
Debugging your setup, and running in local mode . . . . . 13
Sysop-configurable text files . . . . . . . . . . . . . . 16
DESQview, networks, and multiple nodes . . . . . . . . . . 20
Working with a FOSSIL driver . . . . . . . . . . . . . . . 22
Utility programs included with Mail Manager . . . . . . . 23
Security features of Mail Manager . . . . . . . . . . . . 24
Additional features . . . . . . . . . . . . . . . . . . . 26
Mail Manager's main menu . . . . . . . . . . . . . . . . . 29
C)onfigure . . . . . . . . . . . . . . . . . . . . . 29
D)ownload . . . . . . . . . . . . . . . . . . . . . . 33
E)xpedite! . . . . . . . . . . . . . . . . . . . . . 33
Q)uit . . . . . . . . . . . . . . . . . . . . . . . . 33
H)elp . . . . . . . . . . . . . . . . . . . . . . . . 33
I)nformation . . . . . . . . . . . . . . . . . . . . 33
M)essage number (lowest) to extract in each conf. . . 34
U)pload your replies . . . . . . . . . . . . . . . . 34
W)ho's online to RBBS-PC? . . . . . . . . . . . . . . 34
X)pert toggle . . . . . . . . . . . . . . . . . . . . 35
Appendix A: Common problems . . . . . . . . . . . . . . . 36
Appendix B: Contacting the authors . . . . . . . . . . . . 37
Appendix C: How to get the latest version . . . . . . . . 38
Appendix D: Suggestions since the initial release . . . . 39
Appendix E: Acknowledgements . . . . . . . . . . . . . . . 40
Appendix F: For TRULY curious types only . . . . . . . . . 42
Appendix G: Mail Manager's file formats (for programmers) 43
INTRODUCTION Page 1
------------
The 'QWK' format has been around for some time now (on bulletin
board systems other than RBBS-PC), and is intended as a
standardized way to transfer mail, news, and bulletins to and
from your bulletin board, and your users.
Mail Manager was conceived as a way to handle RBBS-PC message
bases offline, via this 'QWK' format used by popular mail readers
such as SLMR, JABBER, OFFLINE, OLX, and many others.
This type of mail transfer is normally a four-step process:
1) The users call your BBS, open the QWK-style mail door,
and download their *.QWK mail packets.
2) The users then log off the BBS, and use any number
of QWK-compatible offline mail readers to read and reply
to messages contained in the mail packets. When they
exit their mail readers, any messages entered in that
session are packed up into what is termed as "reply
packets".
3) The users then call your BBS back up, open the QWK-style
mail door, and upload their reply packets (*.REP).
4) The QWK-style mail door then processes the reply packet,
and inserts the new messages into the proper message
base(s).
Enter RBBS-PC and Mail Manager.
The original purpose was to create a small, secure, functional
door for our users here on our own 3-node RBBS-based system, but
has since expanded quite a bit beyond what we had originally
intended (to put it mildly).
We acknowledge that there are at least two other QWK mail doors
for RBBS-PC message bases (with an additional one on the way):
JIMMER by Jim Goodenough,
TQM by Tom Collins, and
an enhanced Mail Manager! (see next page)
JIMMER popped up during development of Mail Manager's initial
release, and TQM followed a few months later.
If Mail Manager isn't what you're after, maybe one of these
others are.
Just for the record, Mail Manager has been in nearly continuous
development since late January of 1991.
WARRANTY, DISTRIBUTION, & REGISTRATION Page 2
--------------------------------------
Mail Manager is NOT guaranteed in any way, shape, or form.
Although we have worked very hard to keep Mail Manager compatible
with a wide variety of possible RBBS configurations, we are
forced to deal with two very important aspects of your RBBS-PC:
your USERS files, and your MESSAGES files. While it works just
fine here, there may be differences in your setup that can
cause problems with the Mail Manager/RBBS-PC combination.
THEREFORE:
RUN MAIL MANAGER AT YOUR OWN RISK!
Mail Manager v1.34 may be distributed freely (in un-modified
form), to the far corners of the earth. The one thing that you
*CAN'T* do is charge anything for it.
If you are a shareware distributor/dealer, a normal disk
copying and postage charge is permitted, provided that the
amount required to do so does not exceed the REAL costs.
($5.00 ought to be plenty, in our opinion).
Mail Manager v1.34 continues to be distributed as SysopWare,
meaning that a registration fee is neither required nor
requested once you have determined that the program meets your
needs.
---*** BLATANT ADVERTISEMENT ***---
To put it as simply as possible, the amount of time and money
required to properly support the widespread use of our door has
turned out to be far greater than we ever imagined.
Future releases which take Mail Manager beyond where it is today
will be released as a new package, which will be our continuing
effort to provide additional features and enhancements to our
door. We're hoping for the first release of this enhanced
version sometime in the summer of 1992.
The enhanced version will have a $25.00 registration fee. We're
not attempting to get rich here, just trying to cover some of
the cost of support. As a sysop, you already know what it costs
for any LD connect time at all...
If you want to be one of the first recipients of the enhanced
version, we are accepting pre-registrations. We'll ship it
to you on disk with registration code as soon as it becomes
available, a few days BEFORE it is made publicly available.
Please see ENHANCED.DOC if you're interested.
We will continue to support the "free" Mail Manager as we have
in the past, and will continue with any bug fixes and/or
modifications for compatibility with future releases of RBBS-PC.
FEATURES/LIMITATIONS Page 3
--------------------
The length of this list has gotten ridiculous. So, we'll only
list the MAJOR stuff that you might be interested in:
■ Can use a FOSSIL for communications.
■ Supports both DESQview and NetBIOS file & record
locking schemes, as well as file sharing under NetBIOS,
and supports Novell networks.
■ Mail packets can be downloaded in either text or
QWK format. Both types of mail packets can, at
the option of the sysop, contain all sorts of additional
stuff such as bulletins, news, new file listings, etc.
■ Supports the optional multiple message headers that are
likely to be present in the upcoming release of RBBS-PC
v17.4.
■ Supports both types of RBBS-PC message bases, fixed-
length and 'elastic'. (Your message bases are
'elastic' if you have configured them to GROW as
messages are added).
■ Can handle a mix of both 'fixed-length' and 'elastic'
message bases.
■ Multi-node support (up to 36 nodes) via DORINFOx.DEF and
separate subdirectories for each node (built by Mail Manager
on-the-fly).
■ Up to 250 conferences can be configured.
■ Up to 1,000 messages can be extracted & downloaded in any
one mail packet. Subsequent downloads will extract any
additional waiting messages. (1,000 messages means at
least a 300K compressed mail packet).
■ BPS rates up to 38,400, and COM ports 1-4 are supported.
■ Support for non-standard communication ports & IRQ's via
FOSSIL, MAILMGR.PRO, and batch files.
■ X, Y, and Zmodem for file transfers via Forsberg's DSZ,
or you can use our implementation of PROTO.DEF (MAILMGR.PRO)
and configure a number of different protocols.
■ "(R)", when found at the beginning of the subject field of
extracted messages, is stripped from the field. This allows
offline readers to group related messages together, rather
than into one group with "(R)" and one without.
■ *FAST* message extracting and handling of ".REP" uploads.
■ High/low ASCII can be allowed or stripped in each conference.
■ ANSI can be allowed or stripped in each conference.
FEATURES/LIMITATIONS Page 4
--------------------
■ Mail reader tearlines in uploaded messages can be altered
(for possible FIDO compatibility) from "---" to " ", or
left alone for each conference.
■ Extensive security checks.
CHECKLIST OF REQUIREMENTS Page 5
-------------------------
[ ] DOS 3.10 or above.
[ ] Un-damaged RBBS-PC message bases. (Not all are!)
[ ] Separate RBBS-PC users files for each conference/subboard.
[ ] DORINFOx.DEF for remote operation.
[ ] A recent version of DSZ.COM (one that supports the "handshake slow"
command) *IN A DOS PATH!*, or the external protocols of your choice
via MAILMGR.PRO (our implementation of RBBS-PC's PROTO.DEF).
[ ] The environment variable of your choice set to indicate where
Mail Manager is to look for "XFER-[node].DEF" (where [node] is
the node number). XFER-x.DEF is no longer required to be in the
default directory.
[ ] The file compression/extraction programs of your choice in
a DOS path, or wherever you specified them in Mail Manager's
list of archivers (MAILMGR.ARL).
[ ] At least 300K free memory, maybe more.
BEFORE YOU BEGIN Page 6
----------------
*PLEASE READ THIS!!!!!! *********************************************
RBBS-PC has the unique ability to create, read, and manipulate its
own corrupted message bases, without ever telling you that anything's
wrong.
Mail Manager is not as forgiving, and requires that your message bases
be in good condition. It is therefore STRONGLY suggested that you run
some type of a checkout/repair utility against your message bases
BEFORE installing Mail Manager. We've included an alternate utility
to repair/purge your message bases named MailFix, which you can try
out as an alternative to CONFIG.EXE's repair and purge functions.
MailFix is compatible with RBBSMail'ed, MsgToss'ed, and OverMail'ed
message bases (which have differently-formatted message headers), as
well as RBBS-standard message bases. This is in contrast to RBBS-PC's
CONFIG option #185, which simply will not properly handle a message
base that has been manipulated by any of these mail processors.
*PLEASE* take a few minutes to read MailFix's documentation before
you attempt to utilize this program!
In any event, you really SHOULD check out the integrity of your
message bases before attempting to install Mail Manager.
UPGRADING FROM A PREVIOUS VERSION Page 7
---------------------------------
If you are installing Mail Manager for the first time, read the
section entitled "Installing Mail Manager from scratch".
If you are upgrading from either v1.30 or v1.33, you should do the
following:
[ ] Replace your existing MAILMGR.EXE and MAILCFG.EXE programs
with the ones included in this package.
[ ] (Optional) - Run MAILCFG.EXE once against your existing
MAILMGR.CFG file, and save your setup (without making any
changes). All this does is update the version number in
your configuration file.
That's all that's needed.
-----------------------------------------------------------------------
If you are upgrading from v1.20 through 1.24, you should do the following
IN THIS ORDER:
[ ] Copy the supplied UPDATE.EXE to your Mail Manager directory,
and run it once from DOS. This updates your existing
MAILMAN.CFG file to the new format. After doing this, you
can discard UPDATE.EXE.
[ ] Make sure you're in your Mail Manager directory, and rename
MAILMAN*.* to MAILMGR*.*. You can do this easily by typing
the following from the DOS command line:
REN MAILMAN*.* MAILMGR*.*
[ ] Replace files with the ones included in the imbedded MAILMGR.ZIP
as needed:
- MAILMGR.EXE (must)
- MAILCFG.EXE (must)
- *.HLP (optional - wording changes)
- *.MNU (optional - wording changes)
[ ] If you'd like to include ANSI color welcome and exit screens
for your users who are configured as such in RBBS-PC, create
a PRELOGC.RBS and/or EPILOGC.RBS, and place them in Mail
Manager's directory.
[ ] Run MAILCFG.EXE, and set these additional options:
- Whether or not to modify the date/time stamp on uploaded
replies.
- Location (City, State) of your BBS.
- Phone number of your BBS.
-----------------------------------------------------------------------
If you are upgrading from a version older than v1.20, you should do the
following IN THIS ORDER:
UPGRADING FROM A PREVIOUS VERSION Page 8
---------------------------------
[ ] Back up your entire Mail Manager subdirectory, in case you
need anything additional from it later.
[ ] Delete everything from it, EXCEPT the following files:
MAILMAN.USR (Mail Manager's internal user file)
MAILMAN.CFG (Mail Manager's binary configuration file)
MAILMAN.BUL (or whatever you named it, if it exists)
*.RBS (the prelog and epilog screens)
*.MNU (the main menu)
*.PRE (Mail Manager's prelog screen)
Almost everything else about Mail Manager has changed from
previous versions of the program.
[ ] Copy UPDATE.EXE to your Mail Manager subdirectory, and run it
once from DOS to update the format of your configuration file.
When finished, you can discard UPDATE.EXE.
[ ] Make sure you're in your Mail Manager directory, and rename
MAILMAN*.* to MAILMGR*.*. You can do this easily by typing
the following from the DOS command line:
REN MAILMAN*.* MAILMGR*.*
[ ] De-compress the embedded MAILMGR.ZIP to your Mail Manager
subdirectory.
[ ] Read the section in MAILMGR.DOC entitled "SYSOP-CONFIGURABLE
TEXT FILES", and update your files as needed. Most notably:
MAILMGR.ARL
MAILMGR.PRO
MAILMGR.BUL
[ ] Run MAILCFG.EXE, and insure that everything is set properly.
MOST NOTABLY the additional options for:
- type of network to use in local mode,
- type of flow control (handshaking),
- path/filename of the list of new bulletins,
- path/filename of your FMS directory (if you were using NEWFILES),
- path/filename of MAILMGR.PRO,
- path/filename of the list of archivers,
- environment variable to use (DSZLOG or equivalent), and
- whether or not to modify date/time stamp on uploaded replies.
- Location (City, State) of your BBS.
- Phone number of your BBS.
This should be sufficient to get you up and running with this release
of Mail Manager, but if you run into trouble, you'll want to carefully
study the following section of this document.
INSTALLING MAIL MANAGER FROM SCRATCH Page 9
------------------------------------
For the purposes of this document, we'll assume that you named your
Mail Manager directory \MAILMGR off the root.
If for some reason these instructions are not clear to you, or this
is your first attempt at installing a door in your RBBS-PC, there's
really not much that can take the place of RBBS-PC's documentation.
With that said...
Check your environment variables (type "SET" at the DOS prompt).
Both RBBS-PC and Mail Manager use the log file "XFER-x.DEF", where
"x" is the node number. Mail Manager needs an environment variable
to determine where this file is located on your system. Most of us
seem to be using Forsberg's DSZ for file transfers, so there should
be a line referencing "DSZLOG", which would look something like this
for node 1:
DSZLOG=C:\RBBS\XFER-1.DEF
or...
DSZLOG=XFER-1.DEF
If Mail Manager cannot find "XFER-x.DEF", it will report that all
file transfers have failed.
In any case, make a note of the environment variable name (in this
case DSZLOG), since you'll need it later.
Once you're past this, you can get on to the actual installation.
Create a subdirectory just for Mail Manager. Stick it anywhere you
want, and name it anything you want, just be sure that it is a drive
and directory specificially meant for Mail Manager. From here on
we'll just refer to it as the \MAILMGR directory.
De-compress the imbedded archive "MAILMGR.ZIP" to the directory you
just created.
Change to it (making it the current directory).
Before you run Mail Manager's configuration program (MAILCFG.EXE),
look for seven files in your Mail Manager directory:
- PRELOG.RBS (and PRELOGC.RBS)
- EPILOG.RBS (and EPILOGC.RBS)
- MAILMGR.BUL
- MAILMGR.ARL
- MAILMGR.PRO
These are all text files, and should be edited to pertain to
your individual RBBS-PC! To take them individually:
INSTALLING MAIL MANAGER FROM SCRATCH Page 10
------------------------------------
- PRELOG.RBS is the welcome message that your users will
see when they first fire up their mail reader against
one of Mail Manager's QWK's. Probably the most common
thing that you'd want to put here would be a copy of your
RBBS-PC prelog or welcome screen, but this is entirely
up to you! (PRELOGC.RBS is an ANSI color version).
--------------------------------------------------------------
- EPILOG.RBS is the signoff message that the users will
see just as they exit your QWK packet from their mail
reader. You might want to put an adaption of RBBS-PC's
EPILOG.DEF here. (EPILOGC.RBS is an ANSI color version).
--------------------------------------------------------------
- MAILMGR.BUL is the list of bulletin path/filenames that
you'll want to include in your user's QWK's. Edit this
file to pertain to your system bulletins, (and/or any
other text files that you'll want to include in your
users' QWK packets), and if any of them are newer than
the user's last call to RBBS-PC, the user will get them
included in his/her QWK packet. The users have the
option of turning "off" new bulletin listings, so if
you have any that you ALWAYS want included in the mail
packets (if they have been updated), precede them with
a double-asterisk:
c:\bulet1 (optional)
**c:\bulet2 (mandatory for inclusion)
You can choose the path\name of this file in the configuration
program. C:\MAILMGR\MAILMGR.BUL is simply the default name.
--------------------------------------------------------------
- MAILMGR.ARL is the list of archivers available to your users.
This is a "template" file, similar in structure to RBBS-PC's
PROTO.DEF. This file is well-commented, and you should be able
to follow what it does fairly easily. If you do not intend to
make a variety of archivers available to your users, simply
delete all compression types except your default, and the users
will be unable to select any other type of file compression.
Be sure to adjust the path to the archiver, if it is not included
in your DOS path.
You can choose the path\name of this file in the configuration
program. C:\MAILMGR\MAILMGR.ARL is simply the default name.
--------------------------------------------------------------
INSTALLING MAIL MANAGER FROM SCRATCH Page 11
------------------------------------
- MAILMGR.PRO is an adaption of RBBS-PC's PROTO.DEF file, to
list the file transfer methods available to your users. You
should be able to use your own PROTO.DEF file here, provided
that the very last protocol option begins with the letter "N",
for "None". Mail Manager is able to use quite a few of the
PROTO.DEF options, such as whether or not a reliable connection
is required, the factor to determine transfer times, and all of
the "template" variables, such as [FILE], [PORT#], [BAUD], etc.
You'll want to insure that the proper DOS path to the file
protocols are listed in the "send" and "receive" arguments,
as well as insuring that you have an external X) and Y)modem
configured. (Mail Manager cannot use RBBS-PC's internal X and
Ymodem). Consult the RBBS-PC documentation for more particulars
regarding PROTO.DEF.
You can choose the path\name of this file in the configuration
program. C:\MAILMGR\MAILMGR.PRO is simply the default name.
(These five are also covered in the section regarding
"SYSOP-CONFIGURABLE TEXT FILES" elsewhere in this manual).
Run MAILCFG.EXE, and inform Mail Manager about your system. You'll find
that it asks a lot of questions! All should be fairly self-explanatory,
but you'll want to read MAILCFG.DOC if you have any questions.
When done, Mail Manager's configuration file (MAILMGR.CFG) will be
created, and thereafter you can edit it anytime by re-running
MAILCFG.EXE.
Follow standard procedure for adding a new door to your system. On
a 'normal' RBBS-PC this would entail:
- Editing MENU5* (or whatever you have named your door menu)
and adding the word " MAILMGR ".
- Creating a MAILMGR.BAT file, and sticking it where RBBS can
find it. Your batch file that calls Mail Manager is very
important, and must logically do the following:
* Change to the Mail Manager directory,
* Copy RBBS-PC's DORINFOx.DEF to that directory,
* Run MAILMGR.EXE, passing the NODE NUMBER as the
ONLY command line parameter (such as MAILMGR 1
for node 1), and
* Change back to RBBS directory when finished.
INSTALLING MAIL MANAGER FROM SCRATCH Page 12
------------------------------------
With that in mind, your batch file should look something
like this:
cd\mailmgr
copy \rbbs\dorinfo%1.def
mailmgr %1
cd\rbbs
If you're running the new "DOORS.DEF" method that RBBS-PC provides,
here's an example line to implement Mail Manager:
MAILMGR,5,,D,"MAILMGR.BAT [NODE]",N,,
This line tells RBBS-PC the following:
1) The name of the door is MAILMGR.
2) Security level 5 and above can access the door.
3) No questionnaire is to be invoked.
4) Exit to this door. (Mail Manager requires a lot of RAM)
5) The name of the batch file to invoke is MAILMGR.BAT.
6) RBBS-PC is to pass the node number to the batch file.
* NOTE - Type the word "[NODE]" as shown above, and RBBS-PC
will replace it with the true node number when it
calls the batch file. If you are running a single-
node system, and find this confusing, you can
instead pass the node number directly, but it isn't
necessary to do it this way. This would make your
DOORS.DEF line look something like this:
MAILMGR,5,,D,"MAILMGR.BAT 1",N,,
7) Don't ask for a password when returning back to RBBS-PC.
8) Don't display a text file when the door closes.
9) Use the time limit from RBBS-PC as the time allowed in the door.
And that's all that's needed.
DEBUGGING YOUR SETUP, AND RUNNING IN LOCAL MODE Page 13
-----------------------------------------------
Assuming (again) that your Mail Manager directory is named \MAILMGR:
Change to the \MAILMGR directory, and run MAILMGR.EXE with no
command line to bring the door up in local mode.
NOTE - Depending on how many conferences you've entered, Mail Manager
may take a while to come up. Mail Manager attempts to find the
user in each and every conference as soon as it loads to
determine which conferences the user has and has not joined.
The more conferences you have, and the slower your hard disk,
the longer this will take. This is required by the security
measures mentioned in the 'features' section.
If this is a first-time installation, Mail Manager should say that you're
a new user and walk you through the user setup.
We think it is necessary to mention Mail Manager's own running scenario,
since it is important for you as the sysop to understand this for any
debugging purposes on your end.
You created +-- Work directories created & maintained by Mail Manager.
| |
\MAILMGR |
|
\MAILMGR\LOCAL
\NODE1
\NODE2
...etc.
Mail Manager changes to these work directories as it runs, and changes
back to the parent directory just as it exits.
Two files that absolutely MUST be in the directory that you created:
MAILMGR.EXE, and RBBSQWK.BAT.
Don't rename RBBSQWK.BAT!!!
You can edit RBBSQWK.BAT if you are familiar with the format of the
CONTROL.DAT file that is included in all .QWK packets, and/or want
to modify what the users will receive in their QWK's. This is not
for the faint of heart, requires some knowledge of how things work
in QWK land, and simply isn't necessary. RBBSQWK.BAT is run each
time that Mail Manager creates a QWK packet for the user to download,
and doesn't do anything at all if you are using MAILMGR.ARL.
FOR A FIRST-TIME INSTALLATION, DON'T MODIFY RBBSQWK.BAT!
An important consideration is what to do with your own personal
QWK's and REP's created locally. Configure your offline reader
to use the \MAILMGR\LOCAL directory for all .REP's and .QWK's,
since that's where Mail Manager will manipulate your mail in
local mode.
DEBUGGING YOUR SETUP, AND RUNNING IN LOCAL MODE Page 14
-----------------------------------------------
To stick a .REP packet into your message bases, just U)pload
while in local mode, and select any protocol other than N)one.
If your .REP packet is in the \MAILMGR\LOCAL directory, it
will be processed as if you'd uploaded the file remotely.
It is important to make you aware that there is a sysop-only menu
option available, and that's "I" (Info), which isn't listed in
either the command prompt, or the menu itself. This menu option is
available only to those with sufficient security to read ALL messages,
or greater. If the user does not have at least this security level,
they will see the familar "Command not recognized", instead.
If you have set yourself up with sufficient security to use this
option, pressing "I" at Mail Manager's main menu will greet you
with something like this:
SYSOP INFORMATION:
Mail Manager version ............: v1.34
Mail Manager path ...............: C:\MAILMGR
MailMGR's operating environment .: LANtastic v4.00 (NetBIOS)
DOS version .....................: 5.00
DOS SHARE detected? .............: Yes
Flow control method .............: Local mode
Free string space ...............: 23624
Non-string array avail ..........: 373408
Available stack space ...........: 1738
MAIN message base ...............: E:\RBBS\MAINM.DEF
MAIN users file .................: E:\RBBS\MAINU.DEF
Highest message # in MAIN .......: 6132
Last msg # YOU read in MAIN .....: 6131
Filename of protocol definitions : C:\MAILMGR\MAILMGR.PRO
Filename of list of archivers ...: C:\MAILMGR\MAILMGR.ARL
Filename of FMS directory .......: E:\RBBS\MASTER.DIR
RBBS-PC semaphore file ..........: E:\RBBS\IBMFLAGS
MailMGR semaphore file ..........: MMFLAGS
RBBS-PC semaphore file size (6) .: 6
MailMGR semaphore size size (3) .: 3
These 20 are all of the possible lines that can be shown to you.
The last four will be displayed only if your environment is
NetBIOS.
Some of the more important information in here:
Mail Manager path should reflect the drive and directory that
you have installed the program in. If it doesn't, your batch
file is probably not changing to the proper directory prior
to running MAILMGR.EXE.
Mail Manager's operating environment should reflect what you've
told Mail Manager to use. If it doesn't, there's definitely a
problem!
DOS version must be 3.10 or above in order for Mail Manager to
operate properly.
DEBUGGING YOUR SETUP, AND RUNNING IN LOCAL MODE Page 15
-----------------------------------------------
DOS SHARE must be detected if you are operating in a NetBIOS
environment. The only exception is if you are running under
a NOVELL network, in which case SHARE checking is bypassed.
Flow control method can report one of five things: Local mode,
FOSSIL, RTS/CTS, XON/XOFF, or NONE. This is a great way to
find out for sure (when calling remotely) if Mail Manager properly
detected your FOSSIL driver. If it didn't, it will show one
of the other flow control options.
Free string space is pretty darned important, too. This
should really be up around 6000 or higher at all times when
you display this screen. It could conceivably be less than
that if you have an extremely large number of conferences,
and/or have a very long path name to all of your conferences,
and/or are running Mail Manager in very tight RAM. If the
number you get here is less than 6000, we want to hear about it!
Non-string array available should be approximately the amount
of free DOS memory that is available to Mail Manager, and this
number is roughly what is available for DSZ and your file
compression/extraction programs. If this number is less than
200K, you are likely to run into trouble, and should check
to make sure that you are EXITING, (NOT SHELLING!) from RBBS-PC
to Mail Manager. This is the only way that we can think of that
would cause you to have less than 200K available on today's
640K+ PC's.
MAIN message base and user file names must match what is true
for your MAIN area. If not, you don't have MAIN as your 1st
conference listed, and Mail Manager will NOT operate properly.
Highest message number in MAIN, and highest message # that
you read in main should be accurate. If they're not, then
Mail Manager didn't properly find you in the MAIN users file,
and/or it wasn't able to correctly access the MAIN message
file.
Filename of list of protocol definitions should match what
you told MAILCFG to use for MAILMGR.PRO.
Filename of list of archivers should match what you told
MAILCFG to use. (If this file does not exist, Mail Manager
will use the default type of compression that you chose, and
will require said archiver to be in a DOS path!)
Filename of FMS directory should match what is true for
your system if you are using an RBBS-PC FMS directory, or
"NONE" otherwise.
The last four lines will only be shown to you if you are
running under NetBIOS, and they are described in better
detail elsewhere in this manual.
If, after following these instructions, you continue to have
trouble, take a look at the "COMMON PROBLEMS" section of this
manual.
SYSOP-CONFIGURABLE TEXT FILES Page 16
-----------------------------
(All in Mail Manager's directory)
MAILMGR.HLP - The online help file that will be displayed to
the users. You can customize it if need be,
but should be pretty much OK as-is.
MAILMGR.PRE - The initial screen displayed when Mail Manager loads.
Again, you might want to customize it for your own
individual system, but it is generic enough as-
distributed that you may not need to.
MAILMGR.MNU - Mail Manager's main menu, displayed to the users
just before the command prompt.
PRELOG.RBS - The welcome message that your users will see when
they first fire up their mail reader against one
of Mail Manager's QWK's. Probably the most common
thing that you'd want to put here would be a copy of
your RBBS-PC prelog or welcome screen, but this is
entirely up to you!
EPILOG.RBS - The signoff message that the users will see just as
they exit your QWK packet from their mail reader.
You might want to put an adaption of RBBS-PC's
EPILOG.DEF here.
MAILMGRC.HLP \
MAILMGRC.PRE \
MAILMGRC.MNU > Color/ANSI versions of the above.
PRELOGC.RBS /
EPILOGC.RBS /
MAILMGR.BUL - The list of bulletin path/filenames that you'll want
to include in your user's QWK's. Edit this file to
pertain to your system bulletins, (and/or any other
text files that you'll want to include in your users'
QWK packets), and if any of them are newer than the
user's last call to RBBS-PC, the user will get them
included in his/her QWK packet.
Bulletins preceded with a double-asterisk are
considered mandatory for inclusion in the user's
mail packets, and if new, they will be included
regardless of whether or not the user has configured
Mail Manager to send new bulletins.
Example:
c:\bulet1
c:\bulet2
**c:\bulet3
bulet1 and bulet2 are optional, bulet3 will always
be included.
SYSOP-CONFIGURABLE TEXT FILES Page 17
-----------------------------
(NOTE - The path\filename of MAILMGR.BUL is
sysop-configurable in MailCFG.EXE.)
MAILMGR.PRO - A copy of the RBBS-PC PROTO.DEF that you intend to
have Mail Manager use. Mail Manager can use all of
RBBS-PC's "template" variables in here, such as
[NODE], [PORT#], [BAUD], etc. Refer to the RBBS-PC
documentation for information on these "template"
variables.
For Mail Manager's purposes, it is important that you
configure "N)one" as the last protocol in this file!
You will also need to configure an external X)modem
and Y)modem, since Mail Manager obviously cannot use
RBBS-PC's internal X and Y that are probably listed
in your existing RBBS-PC PROTO.DEF.
The supplied MAILMGR.PRO will use X, Y, and Zmodem
in the same fashion as previous versions of Mail
Manager, requiring DSZ.COM to be in a DOS path.
(NOTE - The path/filename of MAILMGR.PRO is
sysop-configurable in MAILCFG.EXE).
HANDLING NON-STD PORTS VIA MAILMGR.PRO
--------------------------------------
In order to support a nonstandard port address in MAILMGR, have your
MAILMGR.PRO specify a custom batch file, rather than a direct call to
the protocol executable itself. Your custom batch file can then send
the correct commands to the protocol, depending on which port is
involved.
Here's what an entry in the MAILMGR.PRO file might look like. This
should all be on one line, of course, but is split here for clarity):
"Z)modem (Batch)",0,S,8,,B,1024,,0.95,,1=E,
"X:\ZMODEM.BAT S [PORT#] [BAUD] [FILE]",
"X:\ZMODEM.BAT R [PORT#] [BAUD] [FILE]"
With drive X: of course being whatever drive\directory you want.
Then the ZMODEM.BAT file could look something like (assuming that you
have ports 1 and 2 at standard addresses, and port 3 at non-standard
address 3e8, irq 5):
@ECHO OFF
: --------------------------------------
: 1st arg is either S or R,
: 2rd arg is comm port number
: 3rd arg is bps rate, and
: 4th arg is filename being transferred.
: --------------------------------------
SYSOP-CONFIGURABLE TEXT FILES Page 18
-----------------------------
IF (%1)==(S) GOTO SEND
IF (%1)==(R) GOTO RECEIVE
GOTO END
:SEND
IF NOT (%2)==(3) dsz port %2 speed %3 sz -m %4
IF (%2)==(3) dsz portx 3e8,5 speed %3 -m sz %4
GOTO END
:RECEIVE
IF NOT (%2)==(3) dsz port %2 speed %3 rz %4
IF (%2)==(3) dsz portx 3e8,5 speed %3 rz %4
:END
This could, of course, be refined into a single batch file that handles
all protocols, not just Zmodem, but it should serve to illustrate the
principle. Or a separate batch file could be set up for each protocol.
We leave it to you to adapt to protocol drivers other than DSZ.
MAILMGR.ARL - The list of archivers that are available to your
users through Mail Manager. MAILMGR.ARL is a
"template" file, similar in structure to
MAILMGR.PRO.
The supplied copy of MAILMGR.ARL allows the use of
ARC, ARJ, LZH, and ZIP compression methods, which
the user can pick and choose from to suit their
own preference. You can configure fewer or additional
archivers as you see fit. Format of each line:
Name, EXT, Compress, Extract
Name = The name of the archiver, as shown to the user.
EXT = The three-letter extension that this archiver
creates by default for compressed files.
Compress = The line to send to DOS to compress the mail
packets.
Extract = The line to send to DOS to extract the uploaded
reply packets that the user uploads.
"Template" variables that can be included in the
Compress and Extract lines (Mail Manager will convert
these to their true values):
[FILE] - Compressed file to create, or extract from.
[INC] - All files that Mail Manager normally
includes in the downloadable archive.
[REPLY] - Reply file that Mail Manager expects to be
contained within the compressed upload.
[NODE] - Current RBBS-PC node number.
SYSOP-CONFIGURABLE TEXT FILES Page 19
-----------------------------
See the supplied MAILMGR.ARL for an example implementation of this file.
(NOTE - The path/filename of MAILMGR.ARL is sysop-configurable in
MAILCFG.EXE).
DESQVIEW, NETWORKS, AND MULTIPLE NODES Page 20
--------------------------------------
Operating in a multitasking environment or on a network is a
special case, worthy of further explanation!
First off, Mail Manager can automatically detect the following
conditions:
- Is DOS SHARE installed?
- Is DESQview present?
- Is Artisoft's LANtastic present?
- Is Novell present?
What Mail Manager detects will be used as the basis for initially
determining the operating environment, which will be:
- DESQview, if it is present, regardless of whether or
not SHARE is installed.
- NetBIOS, if DESQview is not present, and SHARE is
installed, or Novell is detected.
- Good ole' normal DOS if neither of the above is true.
Mail Manager will then use the appropriate file locking technique
for the type of environment that was detected. At this point,
the only file being accessed is Mail Manager's own configuration
file, so your RBBS files are quite safe even if this is not
the same environment that you have specified for RBBS to use.
Once the program has progressed far enough to have read what
network type that you told it to use (from DORINFOx.DEF if
operating remotely, or MAILMGR.CFG if operating in local mode),
Mail Manager will, if necessary, switch to your specified type
of network.
With that out of the way, let's talk about the three possible
types of environments, and what they mean from Mail Manager's
standpoint:
DESQview - Mail Manager will use the same file & record locking
scheme that RBBS-PC itself uses. In fact, it uses the
very same assembler source, which was written by Jon
Martin in 1988. Therefore, the DESQview semaphore locking
routines used by Mail Manager are copyrighted by Jon Martin,
and are in fact available to anyone who has a copy of
RBBS-PC's source code. Look for RBBSDV.ASM in RBBS-PC's
assembler source.
--------------------------------------------------------------------------
NetBIOS/ - This is a special case, and requires that physical file
Novell and record locking take place. RBBS-PC uses what is
termed as a "semaphore" file, to control access to
what Mail Manager is concerned with: Your USERS file(s),
your MESSAGES file(s), and your FMS file (if any).
DESQVIEW, NETWORKS, AND MULTIPLE NODES Page 21
--------------------------------------
This is done with the hard-coded filename "IBMFLAGS",
which will exist in the same directory as your MAIN
message base. If you're already running RBBS-PC
under NetBIOS, look for it... it should already be
there. IBMFLAGS is 6 bytes in length, and contains
nothing but three empty 2-byte records, which are
controlled by RBBS-PC (and now Mail Manager) to limit
access to USERS and MESSAGES files.
Under NetBIOS, Mail Manager will create and maintain its
own "semaphore" locking file, using the same principle
as IBMFLAGS. Mail Manager's semaphore file is named MMFLAGS,
and will be created in your Mail Manager directory. MMFLAGS
will be 3 bytes in length, and manipulated by all nodes
of Mail Manager.
It is also noteworthy to mention that all files will be
opened in a SHARED fashion under NetBIOS, which is
the nature of the beast.
If you are running under Novell Netware, Mail Manager
will detect it, and will not check for the installation
of DOS SHARE. If Novell is not detected, yet NetBIOS
is specified as the environment, Mail Manager will check
for DOS SHARE before allowing itself to continue.
--------------------------------------------------------------------------
DOS - Gee, isn't it nice when you don't have to worry about all
this? Under good 'ole DOS, none of the above is meaningful,
and all files will be opened normally, with no locking
mechanisms in place.
If you happen to be running in an environment that does NOT match
any of the above three methods, AND you are sharing the same set
of RBBS message bases and users files between nodes, you will want
to consider having DOS SHARE loaded, and configure both RBBS-PC
and Mail Manager to use NetBIOS as the operating environment.
Or, if file sharing is not a concern, just configure Mail Manager to use
DOS as its environment.
You should NOT set up a separate Mail Manager configuration for each node
unless your network drive letters are different on each one:
(C:\MAINM.DEF on one, D:\MAINM.DEF on another).
Why you'd set your network up that way we don't know, but it isn't
our place to, is it? Mail Manager always operates out of a unique work
directory for each node, and can handle up to 36 nodes with a single
configuration.
WORKING WITH A FOSSIL Page 22
---------------------
Starting with version 1.10, Mail Manager does support a FOSSIL driver.
If you told RBBS-PC to use a FOSSIL, Mail Manager will also. Versions
1.10 and up have been tested successfully with both BNU v1.70 and X00
v1.2x FOSSILs.
PLEASE NOTE that some door converters & programs that 'launch'
doors for you may not correctly set the FOSSIL argument in
DORINFOx.DEF!!!!
The very last line of your DORINFOx.DEF (line #13) should be either
a zero or minus one (0 or -1). -1 indicates that the FOSSIL is
active in RBBS-PC, and tells the door that it too should use a FOSSIL.
To keep you from having to dig up the RBBS-PC documentation, here's
what Mail Manager expects from DORINFOx.DEF:
NEWARK CONNECTION <- BBS name (ignored by Mail Manager)
CHIP <- Sysop's first name
MORROW <- Sysop's last name
COM1 <- Communications port
2400 BAUDD,N,8,1 <- Communications parameters
6 <- Network type (4=DV, 6=NetBIOS)
JOE <- User's first name
USERNAME <- User's last name
NEWARK, OH <- User's city/state
2 <- User's graphics preference (2=ANSI)
10 <- User's security level
30 <- Number of minutes remaining
-1 <- FOSSIL in use (0=no, -1=yes)
* NOTE - The second "D" in "BAUDD" is a bug in RBBS-PC 17.3C, and
does not affect Mail Manager's operation.
It is possible to configure Mail Manager to ALWAYS check for a FOSSIL
driver, regardless of the setting in DORINFOx.DEF. This is done
in the MAILCFG program, by setting the flow control method to
"F". In this case, Mail Manager will ALWAYS try to use a FOSSIL
for communications. See MAILCFG.DOC for further details.
UTILITY PROGRAMS INCLUDED WITH MAIL MANAGER Page 23
-------------------------------------------
We include two supplemental programs with Mail Manager:
MAILCFG.EXE - The configuration program, which is required
to create Mail Manager's configuration file,
MAILMGR.CFG. Once created, MAILMGR.CFG
can be edited anytime by re-running this
program.
MAILFIX.EXE - A handy little program to check/repair/purge/
re-size your message bases. It is compatible
with RBBSMail, OverMail, and MsgToss, as well
as RBBS-PC itself, and can handle both
fixed-length and 'elastic' message bases.
These utilities are explained in further detail in the their individual
documentation (MAILCFG.DOC, and MAILFIX.DOC).
SECURITY FEATURES Page 24
-----------------
Mail Manager has extensive built-in security functions. We hope
you agree that it does make for a pretty secure mail door.
We want to make you aware of the importance of the security level
that you configured in the MAILCFG program for the ability to read
ALL messages. This security level is checked for all of the sysop
functions that Mail Manager performs, and should be set to either
sysop or co-sysop level. Some of the more important things that
users with this security level or higher can do:
- Use the sysop-only function I)nfo from the main menu (which
shows where everything that pertains to your Mail Manager
setup is located).
- Upload a message under a name other than the one that they
use on the BBS.
- Read everybody's mail, regardless of whether it's marked as
private or password-protected.
You get the idea.
------------------------------------------------------------------
Conferences are configured with two minimum security levels: One
for the ability to read, and the other for the ability to post.
User can only extract mail from conferences that they have joined
from the BBS.
Mail Manager will not add a user to a conference in any case.
Mail Manager bypasses all killed messages.
Only conferences which the user has joined are shown in the QWK
packets that the user downloads.
Password-protected messages are only extracted and downloaded to
users with an exact name match in the "TO" or "FROM" fields, or
to those with sufficient security to read ALL messages.
Only users with sufficient security to read ALL messages are
permitted to upload messages under a name other than the one
they use on the BBS.
Users cannot upload messages to conferences that they have not
joined.
SECURITY FEATURES Page 25
-----------------
Mail Manager posts a private message (in the MAIN area) to the
sender's true name whenever a security violation regarding an
uploaded reply occurs. This can be triggered by:
- Uploading a message with the "FROM" name not matching
the user's name on the BBS.
- Uploading a message to a conference that the user has
not joined.
- Uploading a message to a conference that the user does
not have sufficient security to post a message in.
- Uploading a message to a conference number that does
not exist.
ADDITIONAL FEATURES Page 26
-------------------
CHAT MODE: While Mail Manager is waiting for a keystroke (preferably
[F10] at the MAIN MENU), the Sysop can press [F10] to jump into
a no-frills chat mode with the user that's currently
online.
When finished with the chat, either one of you can type
"/QUIT" to return to Mail Manager.
----------------------------------------------------------------------
DOS SHELL: While Mail Manager is waiting for a keystroke (preferably
[F2] at the MAIN MENU), the Sysop can press [F2] to jump to DOS.
When finished, type EXIT to return to Mail Manager.
Naturally, this works only from the local keyboard. Mail
Manager will automatically return to the proper drive and
directory when you type "exit" to return from the DOS shell.
----------------------------------------------------------------------
TIME LIMIT: This is passed to Mail Manager from RBBS-PC in DORINFOx.DEF.
It will be either the amount of time remaining on your
RBBS-PC, or whatever time limit that you specified in
DOORS.DEF, otherwise. In local mode, the time limit is
always 120 minutes.
----------------------------------------------------------------------
KYBD IDLE: If Mail Manager has to wait more than 180 seconds for the
user to press a key, it will exit back to the BBS.
The user will get a beep and a warning message after 90
seconds, and every 30 seconds thereafter, until keyboard
time expires.
----------------------------------------------------------------------
CARRIER DETECT: If the user drops carrier, Mail Manager will report
to you as such, write this info to the appropriate log
file, and return to the BBS. RBBS-PC will see that no
carrier detect is present, re-cycle itself, and wait
for the next caller.
----------------------------------------------------------------------
DOWNLOAD & EXIT: Although the E)xpedite! option is documented
elsewhere in this manual, we didn't make it clear as to the
best way to automate this from RBBS-PC's standpoint.
RBBS-PC 17.3C and above allow you to specify "/G" after
the name of the door, which allows the user to be logged
off immediately after returning to RBBS-PC. Therefore,
the user could type:
d mailmgr /g
Then, from within Mail Manager, select E)xpedite!, and the
user will be logged completely off the BBS after downloading
their mail.
----------------------------------------------------------------------
ADDITIONAL FEATURES Page 27
-------------------
NEW FILES: If you are running a standard RBBS-PC FMS directory, you
should be able to use this built-in capability. If you are
not running a standard FMS, and the path/name of your FMS
directory is set to "NONE" in the MAILCFG program, Mail
Manager will not attempt to include a new file listing in
the user's mail packets.
It should be noted here that the users do have the ability
to turn this feature "off", if they do not desire a file
listing in their mail packets.
Here's what is required of your FMS directory:
- No 'special' lines contained within it (semi-private
filenames preceded with an asterisk (*) before the
filename, special comment lines, etc).
- Oldest files listed at the top of the FMS, and most
recent files listed at the bottom.
If yours fits all of the above, NEWFILES should work fine.
Here's the way NEWFILES works:
1) Finds the date that the user last checked the file listing
(from the RBBS-PC main users file). If user never listed
your file directories, the user's last date into the
Mail Manager door is used, instead.
2) Grabs the very first line of your FMS, to determine the
line length, since this can vary depending on how you set
things up via RBBS-PC's CONFIG. HOWEVER, all lines in your
FMS are expected to be the same length as the first line
listed!
3) After determining line length, moves to end of file, grabs
the very last line of your FMS, and checks the date stamp
against the user's "last check" date.
4) If the last file's date is the same as, or newer than, the
user's date that they last listed your files, NEWFILES
steps through your FMS in reverse order, pulling out
filenames & extended descriptions until the date stamp is
earlier than the user's last check. The file created
(NEWFILES.DAT) is then included in the user's QWK mail
packet, and can be viewed easily within his mail reader.
If the last file's date is older than the user's last check,
NEWFILES figures no new files, and doesn't include a
NEWFILES.DAT in the QWK packet.
PRIVATE UPLOADS TO THE SYSOP are included ONLY in the sysop's
own mail packets. These files (and their extended
descriptions) are skipped for everyone else.
ADDITIONAL FEATURES Page 28
-------------------
If you use chained FMS directories, or any of the "\FMS"
directives, NEWFILES will stop searching when it reaches that
line of your FMS. Why? The line won't be an extended
description (" ." as the last three characters on the line),
and won't have a file date in the proper positions on the
line. In this case, NEWFILES will consider the file date to
be 00-00-00, and will quit searching your FMS directory.
THE MAIN MENU Page 29
-------------
Although we hope that you'll find Mail Manager to be pretty self-
explanatory, a complete run-down on everything that you can do
with this door follows.
A shorter version of this is available to the user, in the
online help file MAILMGR.HLP and MAILMGRC.HLP.
The menu itself looks like this:
MAIL MANAGER Main Menu:
┌────────────────────────────────────────────────────┐
│ C)onfigure Mail Manager. ├─┐
│ D)ownload new mail from your selected conferences. │ │
│ E)xpedite! (Download new mail and return to RBBS) │ │
│ Q)uit (return to bbs) │ │
│ H)elp! │ │
│ M)essage number (lowest) to extract in each conf. │ │
│ W)ho's online to RBBS-PC? │ │
│ U)pload your replies. │ │
│ X)pert toggle (this menu on/off) │ │
└─┬──────────────────────────────────────────────────┘ │
└────────────────────────────────────────────────────┘
Your choice, Username <C,D,E,Q,H,M,W,U,X,?>?
MAIN MENU commands are as follows:
C - Configure Mail Manager.
Allows you to select your personal options, and change your
selected conferences from which to extract new mail. Please note
that you must J)oin the conference from the BBS before you can
extract mail via this door. Otherwise, Mail Manager will not find
you as a valid conference user, and will not access the conference
for you.
You'll be presented with a screen that looks something like this:
----------------------------------------------------------------------
THE MAIN MENU Page 30
-------------
Configuration options:
A - Select conferences to extract and download.
B - Download messages in Q)WK or T)ext format..........: Q
C - Msgs addressed to ALL marked as personal (QWK only): No
D - Extract ONLY your personal mail ...................: No
E - Extract messages written by YOU ...................: Yes
F - Abort packet if no messages .......................: No
G - Send updated bulletins ............................: Yes
H - Send new file listings ............................: Yes
I - Ask before sending packet .........................: No
J - Type of file compression to use ...................: ZIP
K - Default file transfer protocol ....................: Z
L - Tell RBBS that you've read your downloaded messages: Yes
T - Use 'TurboKeys' (act on 1-character commands) .....: No
-----------------------------
Q - Quit. (Finished configuring)
Enter your choice(s), UserName <A,B,C,D,E,F,G,H,I,J,K,L,Q> ->
-----------------------------------------------------------------------
A - Select conferences to extract and download.
You'll be presented with a list of conferences that you
are able to access, which will look something like this:
---------------------------------------------------------------
You may select any conference which is shown in UPPER CASE.
Confs you've marked as active are surrounded in brackets '[]'.
Confs shown in lower case must first be joined from the BBS.
Confs marked as --- are not available.
1 - [MAIN ] 11 - TEEN 21 - [RSYS ]
2 - [4SALE ] 12 - [PRIVATE] 22 - [BITS ]
3 - [MS-DOS ] 13 - [SYSOP ] 23 - [POL ]
4 - BBS 14 - [USER ] 24 - [CRES ]
5 - --- 15 - grafx 25 - [WINB ]
6 - [CODE ] 16 - arj 26 - [MAILMGR]
7 - [DEBATE ] 17 - ---
8 - [HAM ] 18 - [QB ]
9 - HUMOR 19 - [RBBS ]
10 - [IBM ] 20 - [DEV ]
Enter conference number(s) to toggle on/off, or [ENTER] to quit.
->
---------------------------------------------------------------
In this example, all conferences that are available to you
are flagged as active, except BBS (conference 4), HUMOR
(conference 9), and TEEN (conference 11).
THE MAIN MENU Page 31
-------------
If you wanted to mark those three as active, you'd enter:
4 9 11
at the above prompt.
Conferences #5 and 17 are unavailable, meaning that the user
either has insufficient security to access them, or you
(the Sysop) have "reserved" these conference numbers in the
MAILCFG program, for future use.
Conferences #15 and 16 are active conferences, but the user
must join them from the BBS before they will be available
to them via Mail Manager.
B - Download messages in Q)WK or T)ext format
Set to text if you want to use Mail Manager as a simple
"extract and download" system (all messages in a single
continuous ascii file).
Set to QWK if you want to read and reply offline using
a QWK-compatible mail reader like SLMR.
C - Msgs addressed to ALL marked as personal (QWK only)
If set to "Y", Mail Manager will add messages addressed
to "ALL" to your personal index. This applies to QWK
packets only.
D - Extract ONLY your personal mail
If set to "Y", Mail Manager will not extract a message
unless it is addressed to you. (Will also extract msgs
addressed to "ALL" if you have option C set to "Y".)
E - Extract messages written by you
If set to "NO", Mail Manager will not include messages
from you in your packet.
F - Abort packet if no new messages
You might not want to do this if you would still like
to receive new file listings or updated system news or
bulletins.
THE MAIN MENU Page 32
-------------
G - Send updated bulletins
If set to "No", any updated bulletins which the sysop
has designated as mandatory will still be included.
H - Send new file listings
If you select this option, a listing of newly-uploaded
files will be included in your mail packet.
This option may not be operational on all systems.
I - Ask before sending packet
If set to "Yes", will cause Mail Manager to prompt you
whether or not you want to receive the mail packet
that it just created for you. Will otherwise go right
into the download when finished extracting.
J - Type of file compression to use
If the Sysop has activated this option, you can
choose from the file compression utilities offered on
this system (ZIP, ARC, etc.).
K - Default file transfer protocol
Choose from the protcols offered by your sysop (Xmodem,
Zmodem, etc.). If set to N)one, Mail Manager will prompt
you for which protocol to use at each file transfer.
L - Tell RBBS that you've read your downloaded messages
If this is set to NO, both RBBS and Mail Manager will
think that you haven't read the messages that you've
downloaded. (Mail Manager will extract them again your
next time in).
T - Use 'TurboKeys' (act on 1-character commands)
Works like RBBS-PC's toggle of the same name. If set to
Yes, Mail Manager will not wait for [ENTER] when asking
you for input.
Q - Quit. (Finished configuring)
(Or just press [ENTER] to accomplish the same thing).
After this screen, you'll be asked to save your current choices.
You MUST answer "Y" if you want your changes to be saved for
subsequent visits to the Mail Manager door.
(If this is your first time into the door, your changes will
be saved automatically).
--------------------------------------------------------------------------
THE MAIN MENU Page 33
-------------
D - Download new mail.
Will find and extract all new mail from your selected conferences,
in the format that you told Mail Manager to use (Text or QWK).
Mail Manager will then compress the file(s) in your selected file
compression format.
Unless your file protocol is set to N)one, Mail Manager will then
send you the mail packet. If your default protocol is set to N)one,
you'll be asked for the transfer protocol of your choice. If you
choose "N", the file will not be sent to you, and you'll be
returned to the main menu. Otherwise Mail Manager will do its best
to send a compressed version of the mail to you via your selected
choice.
---------------------------------------------------------------------------
E - Expedite!
Same as Download (above), except automatically exits back to
the main bulletin board when finished.
---------------------------------------------------------------------------
Q - Quit (return to BBS).
This one should be pretty self-explanatory.
---------------------------------------------------------------------------
H - (Or '?') Display help file.
Displays an abbreviated version of these command descriptions.
---------------------------------------------------------------------------
I - Sysop Information
This command is not shown in the online help file, is not
displayed in the command prompt, and is not shown in the menu
itself.
Only those with sufficient security to read ALL messages will
be able to activate this command. Everyone else will get the
familiar "Command not recognized".
The purpose of this command is to assist you in debugging your
setup, and it is covered in detail elsewhere in this manual
under "DEBUGGING YOUR SETUP".
--------------------------------------------------------------------------
THE MAIN MENU Page 34
-------------
M - Message number (lowest) to extract in each conference.
Mail Manager will normally download mail based on the last message
that you've read in each conference. Since you can read mail both
online AND offline, and have the option of telling Mail Manager
NOT to update your last message read markers, you might want to
use this option to reset them to what you want.
Requirement for using this option:
- You must have already joined the conference from the main
board (as with all conferences that you manipulate via
this door).
If you get an error while changing your message markers, try going
back through the C)onfigure option, saving your settings, and try
again.
---------------------------------------------------------------------------
U - Upload your replies.
Works with QWK-compatible mail reader/repliers only. Your uploaded
file is expected to be compatible with the .REP format used by
popular mail readers such as SLMR. Mail Manager will look for the
REP packet after the upload and attempt to place your replies into
the proper message bases.
If your default protocol is set to N)one, you'll be asked for the
protocol that you wish to use. If you select N)one, you'll be
returned to the main menu.
If you're in local mode as the Sysop, place the .REP file in the
\MAILMGR\LOCAL directory, and choose this option. This is covered
further in the section regarding "DEBUGGING YOUR SETUP".
---------------------------------------------------------------------------
W - Who's online?
Displays a list of who's online to all nodes of this RBBS-PC.
(Much like RBBS's command of the same name).
Those with sufficient security to read ALL messages will have
the following displayed:
- User's name,
- City/State, and
- Baud rate.
THE MAIN MENU Page 35
-------------
If a node is inactive, the last user's information is
displayed, and will be reported as "Last call".
All other users will have the following displayed:
- User's name, and
- baud rate.
If a node is inactive, "Waiting for next caller" is displayed.
---------------------------------------------------------------------------
X - Expert toggle.
Turns the main menu on or off. (Much like RBBS's command of the
same name).
This setting is saved for the user's next time into the door.
APPENDIX A - COMMON PROBLEMS Page 36
----------------------------
Problem : Not finding the Sysop in any conferences.
Solution: Double-check your setting of "Remote Sysop Name" on the first
screen of the MAILCFG program. This setting must be the name
that you use to log onto your system remotely, NOT your name
as you are known to your users.
--------------------------------------------------------------------------
Problem : Shows "Error finding new message" when trying to extract your
first mail packet.
Solution: Run MAILFIX.EXE against the message base in question (using
the proper command line switches). Re-read the section of
this document entitled "Before you begin".
--------------------------------------------------------------------------
Problem : Always showing Sysop name when operating remotely.
Solution: Probably not copying the correct DORINFOx.DEF file to the
Mail Manager directory prior to loading the door. Drop to
DOS, and take a look at the DORINFOx.DEF that was in use at
the time.
/------------------[ v1.20 to v1.24 ]---------------------\
The authors spent the majority of the development time on
v1.30 extensively tracking a problem that exists only when
Mail Manager is executed on a system that has a math co-
processor installed.
Weird problems prevailed, including:
- Freezing at the "Checking conferences:" prompt,
- Looping back to "Initializing Mail Manager:" after checking
conferences, and THEN freezing,
- Runs ok sometimes, sometimes locks the CPU.
We have spent weeks trying to track this down, and could not
find anything in Mail Manager that could cause such a thing to
happen.
The problem was FINALLY traced to floating point implementation
when running on a co-processor or 486.
We have worked out replacement routines that eliminate *ALL*
floating point calculations from Mail Manager. Test versions
using these routines have fixed the problems on beta test systems
that had trouble with previous versions. With the releases of
v1.30 and up, we believe these problems are a thing of the past.
(Crossing fingers and knocking on wood)
APPENDIX B - CONTACTING THE AUTHORS Page 37
-----------------------------------
Comments, suggestions, ideas, and whatever else you want to throw
our way would be GREATLY APPRECIATED and should be directed to any
of the following:
Good ole' US Mail:
Newark Connections
PO Box 2023
Heath, OH 43056
Or via modem:
Netmail: 8:965/9 (via RBBS-NET)
Data: (614) 366-4392 (SYSOP or DOUG WILSON) *
Compuserve: 72677,502 (Chip Morrow)
Please send any Netmail directly to us, not through
your RBBS-NET host. No sense in having EVERYONE pay
long distance charges for personal messages.
---------------------------------------------------------
--> * PLEASE NOTE that we use PCBVerify as mandatory callback
verification, and do *NOT* manually verify users!
Please see Appendix C regarding a special username/password
combination that you can use to log onto our system without
the registration hassles. If you really need to drop us a
quick note, and can't be instantly verified, that's the
way to do it.
Other ways to find us:
RIME's RBBS and RBBSQWK conferences, followed by Doug Wilson.
FIDO-NET's RBBS-PC and OFFLINE conferences, followed by both
of us.
RBBS-NET's MAILMAN conference, followed by both of us.
We're sorry, but we simply do not have the time or resources to
make individual voice calls to help with debugging your individual
Mail Manager setup.
On the other hand, we'd like to see you in any of the above echo
conferences, where you can get help from others as well as ourselves,
and where questions/answers/reports/release notices get a much wider
audience, and can benefit more people.
APPENDIX C - HOW TO GET THE LATEST VERSION Page 38
------------------------------------------
You can download the latest version of Mail Manager on your first
call by logging onto either of our BBS nodes with the following
user name/password combination:
FIRST name: MAILMGR
LAST name: LATEST
Password: VERSION
You'll have 20 minutes of online time, so after the preliminary
curiosity, do this from the main menu:
Go to the F)iles section. ; F
Select the P)ersonal files option. ; P
From the P)ersonal menu, list the available files, and download
the most recent version of Mail Manager that's listed. You have
unlimited time to download anything listed, but only from that
menu!
Since this logon method will create no record identifying you, we
would very much appreciate it if you would leave a short C)omment to
Sysop telling us who you are and where you are calling from, or
(better yet) J)oin the MMGR conference, and drop a public note in
there. That way your fellow MailManagers <grin> will see that they
weren't the only ones. Not to mention that we'd like to keep the
MAILMGR conference updated and informative!
Public node is (614) 366-4392 (300-2400 baud)
HST node is (614) 366-3494 <- Private node, but still accepts
MAILMGR LATEST.
As MAILMGR LATEST, you can also open the MAIL door on our own system,
and have a glance at what the very latest version (probably in beta
test) looks like.
For those of you who desire to access our board under your own name:
Per APPENDIX B, please note that we use mandatory callback verification
(via PCBVerify) for all new users on our RBBS-PC. If for whatever reason
you cannot be automatically called back via modem, you cannot be verified
as a user on our RBBS-PC, and will have to use the MAILMGR LATEST user
name if you intend to call our system directly.
On the other hand, if you do desire access with your own name, and can
be called back via PCBVerify, you can have full access after two phone
calls. We can't please everybody.
APPENDIX D - SUGGESTIONS SINCE INITIAL RELEASE Page 39
----------------------------------------------
We've had a slew of 'em. Keep 'em coming! We can't get better
without your input.
Most frequent suggestions:
- Easier/faster setup for MANY conferences : done v1.04
- New bulletins included in QWK's : done v1.04
- New NEWS file included in QWK's : done v1.04
- Less screwing around with RBBSQWK.BAT : done v1.04 & v1.10
- NEWFILES.EXE supporting extended descriptions : done v1.04
- Non-standard IRQ and address support : via FOSSIL & PROTO.DEF
- File/Record locking : done v1.10
- Desqview awareness : done v1.10
- FOSSIL support : done v1.10
- Add new bulletins/news to TEXT packets : done v1.10
- Allow configurable type of file compression : done v1.20
- Allow configurable transfer protocols : done v1.20
- Support FIDO-style conferences as well as RBBS:
- Support "net-status" packets from other BBSs :
FOSSIL & DV support were definitely the top two as far as number
of people asking for it. After that were configurable file
compression/extraction & transfer protocols. They took a while to
to implement, but they're in there now.
Support for FIDO-style conferences is currently in beta test, and
will be included in the first of the upcoming enhanced versions.
We are still studying "net-status" packets to see what can be done
there. We have seen lots of example packets, but precious little
in the way of "real" format documentation. If anyone has some hard
format documentation as to what EXACTLY is required for "net-status"
packets, please send it our way! If we manage to get this taken
care of, it will be included in a future release of the enhanced
package.
APPENDIX E - ACKNOWLEDGEMENTS Page 40
-----------------------------
Microsoft, Crescent Software, DSZ, PKZIP, LHARC, ARJ, LZEXE, PKLITE,
Jimmer, TQM, LANtastic, DESQview, BNU, X00, RBBSMAIL, MSGTOSS,
OVERMAIL, PDQ, PDQCOMM, QuickBASIC, RBBS-PC, SLMR, JABBER, OFFLINE,
and OLX (did we miss any?) are all trademarks or copyrighted in some
way by somebody, and are mentioned throughout our documentation for
clarity only.
Special thanks to:
Mike Ervin, who tested early beta versions on his system and
verified that it really worked in an environment other than
our own.
Tom Craver, who tested the very last beta version prior to
the initial release of v1.01b, and helped us get 38,400 bps
taken care of.
Craig Gagner, who actually sent us an exact sample of the
error message reported when opening the communications port
under DESQview. Had LOTS of reports on this one.
Glenn Rossi, who first suggested adding extended description
support, wrote his own converter to handle them, pointed us
in the right direction for DESQview, and tested a late beta
of v1.10 under DESQview for us.
Jon Martin, who was nice enough to supply the world with
assembler source for DESQview resource locking.
Joe Tailleur, who tested several beta versions for us under
DESQview.
Michael Lurie, who put up with seemingly never-ending system
crashes while testing beta copies. Michael, you're a patient
individual!
Gregg Snyder who was the first brave soul to try non-standard
port addresses.
Don Smith, who tested a few late beta versions of v1.24 for
us under Novell.
Doug Azzarito, current co-author of RBBS-PC, who thinks
enough of our door to run it on his own system, and offer
beta-testing.
Dave Brodmann, who's 486 was used as a guinea pig for the
floating point problem, and other experiments. Yet another
patient individual!
Benny Carr, who also has a math co-processor system that
was abused by beta copies.
And thanks to everyone else who commented & offered suggestions,
help, and beta testing. We honestly cannot remember all of the
names, and do apologize for that!
APPENDIX E - ACKNOWLEDGEMENTS Page 41
-----------------------------
We are frankly astounded at Mail Manager's quick success and wide
distribution (we've had file requests from Nova Scotia to Taiwan),
and hope we can continue to provide everyone with a truly useful
piece of software for your RBBS-PC.
Chip Morrow and Doug Wilson
APPENDIX F - FOR TRULY CURIOUS-TYPES ONLY! Page 42
------------------------------------------
Mail Manager's source code is not available. We will, however,
continue to listen to suggestions, and work on improving the
program, as time permits.
For the few who have been curious enough to ask, Mail Manager is a
multiple-module, modern-dialect BASIC program, compiled & linked
using Microsoft's QuickBASIC, and Crescent Software's PDQ and
PDQComm. (We speculate that Mail Manager may have the world's
record for the largest PDQ/PDQComm-specific program to date...
<grin>...).
DEVELOPMENT SITE: Newark Connection RBBS - 3-nodes running under:
- A LANtastic network (2mbps cards),
- DOS SHARE,
- MS-DOS 5.0 (all nodes)
- One 2400 node and one HST (locked at 19.2 via BNU),
- Binkley-Term 2.30,
- RBBS-PC 17.4 beta (as of this writing),
- Node 1 (286-8) - RBBSMail, Qmail
- Node 2 (286-16) - RBBSMail, Qmail
- Node 3 (286-12) - Local Workstation (no modem).
SIDE NOTE REGARDING COMPRESSED EXECUTABLES:
--------------------------------------------------------------
We're distributing the executables in non-compressed format.
You'll find that our .EXE's will compress quite nicely with
utilities like PKLITE and LZEXE. We leave it up to you to use
the compression utility of your choice, or run as-is.
--------------------------------------------------------------
APPENDIX G - MAIL MANAGER'S FILE FORMATS Page 43
----------------------------------------
Just in case someone out there has an inkling to write a utility
program or two for use with their Mail Manager setup, here are the
formats for Mail Manager v1.34's two binary system files, MAILMGR.CFG
and MAILMGR.USR.
+-------------------------------------------------------------------------+
| MAILMGR.USR - Mail Manager's internal users file. |
| One 884-byte record per user. Each 884-byte record is |
| broken down as follows: |
|-------------------------------------------------------------------------|
| Start Stop Length Record Type Description |
|=========================================================================|
| 1 31 31 STRING The user's name, in upper case, |
| left-justified, padded with ASCII 32s|
|-------------------------------------------------------------------------|
| 32 281 250 STRING Conference-active flags. ASCII 1 if |
| flagged as active, ASCII 255 if not. |
| 1 flag for each of the 250 possible |
| conferences. |
|-------------------------------------------------------------------------|
| 282 781 500 STRING UNUSED - This field is now redundant,|
| and will be removed entirely in a |
| future release. |
|-------------------------------------------------------------------------|
| 782 782 1 STRING User's QWK preference. Either "Q" |
| or "T". (QWK or TEXT). |
|-------------------------------------------------------------------------|
| 783 783 1 STRING User's flag for whether or not to |
| update last message read in the RBBS |
| user files (after downloading pkts). |
| ASCII 1 for true, 255 for false. |
|-------------------------------------------------------------------------|
| 784 784 1 STRING Letter of the user's default file |
| protocol choice, in upper case. |
|-------------------------------------------------------------------------|
| 785 785 1 STRING Messages addressed to "ALL" marked |
| as personal in QWK packet? ASCII 1 |
| for true, 255 for false. |
|-------------------------------------------------------------------------|
| 786 786 1 STRING Xpert toggle on or off (ASCII 1, 255)|
|-------------------------------------------------------------------------|
| 787 787 1 STRING Bit flag byte for other user options.|
| Currently used: 0 = Send own msgs |
| 1 = Send bullets |
| 2 = Send newfiles |
| 3 = Abort if no msgs|
| 4 = Ask before send |
| 5 = Only pers mail |
| 6 = Turbokey toggle |
|-------------------------------------------------------------------------|
| 788 790 3 STRING User's choice of archiver (ZIP, ARC, |
| etc.) |
|-------------------------------------------------------------------------|
| 791 796 6 STRING "YYMMDD" that user last used the |
| door. ("911223" = 23 Dec 91) |
|-------------------------------------------------------------------------|
| 797 884 88 STRING Reserved for future use. |
+-------------------------------------------------------------------------+
APPENDIX G - MAIL MANAGER'S FILE FORMATS Page 44
----------------------------------------
+-------------------------------------------------------------------------+
| MAILMGR.CFG - Mail Manager's configuration file. |
| Consists of one 556-byte header, followed by a number of |
| 334-byte conference configuration records. |
| |
| HEADER RECORD: |
|-------------------------------------------------------------------------|
| Start Stop Length Record Type Description |
|=========================================================================|
| 1 35 35 STRING Name of the BBS (in proper case). |
|-------------------------------------------------------------------------|
| 36 66 31 STRING Remote logon name of the sysop (left-|
| justified, in upper case, padded with|
| ASCII 32 blanks). |
|-------------------------------------------------------------------------|
| 67 81 15 STRING Sysop's public first name. |
|-------------------------------------------------------------------------|
| 82 96 15 STRING Sysop's public last name. |
|-------------------------------------------------------------------------|
| 97 98 2 INTEGER Security level to read ALL messages. |
|-------------------------------------------------------------------------|
| 99 100 2 INTEGER Security level to use in local mode. |
|-------------------------------------------------------------------------|
| 101 102 2 INTEGER Local sysop's graphic preference. |
| 2 = ANSI, 1 = ASCII, 0 = None. |
|-------------------------------------------------------------------------|
| 103 163 61 STRING Default tagline for all conferences. |
|-------------------------------------------------------------------------|
| 164 165 2 INTEGER Number of 334-byte conference |
| configuration records that follow |
| this header record. |
|-------------------------------------------------------------------------|
| 166 173 8 STRING First 8 characters of extract file |
| name to use (this is the "*" of |
| *.QWK, *.REP, *.ZIP, etc.). |
|-------------------------------------------------------------------------|
| 174 176 3 STRING 3 upper case characters designating |
| the default file compression type |
| (ZIP, ARC, ARJ, or LZH) |
|-------------------------------------------------------------------------|
| 177 216 40 STRING Full path/filename of the NEWS file. |
|-------------------------------------------------------------------------|
| 217 256 40 STRING Full path/filename of the list of |
| bulletins (MAILMGR.BUL). |
|-------------------------------------------------------------------------|
| 257 257 1 STRING Network type to use in local mode. |
| D)os, N)etbios, desQ)view. |
|-------------------------------------------------------------------------|
| 258 258 1 STRING Handshake method to use, upper case. |
| R)ts, X)on, N)one, or F)ossil. |
|-------------------------------------------------------------------------|
APPENDIX G - MAIL MANAGER'S FILE FORMATS Page 45
----------------------------------------
| 259 260 2 INTEGER Version number (1.34 = 134). |
|-------------------------------------------------------------------------|
| 261 300 40 STRING Path/filename of MAILMGR.PRO |
|-------------------------------------------------------------------------|
| 301 340 40 STRING Path/filename of FMS directory. |
|-------------------------------------------------------------------------|
| 341 380 40 STRING Path/name of list of archivers. |
|-------------------------------------------------------------------------|
| 381 395 15 STRING Name of environment variable to check|
| path/name of XFER-x.DEF log file. |
|-------------------------------------------------------------------------|
| 396 396 1 STRING Modify uploaded messages date & time |
| stamp to the current system time? |
| (Y or N) |
|-------------------------------------------------------------------------|
| 397 427 31 STRING City/State where BBS is located. |
|-------------------------------------------------------------------------|
| 428 439 12 STRING Phone number of BBS. "xxx-xxx-xxxx" |
|-------------------------------------------------------------------------|
| 440 556 117 STRING Reserved for future use. |
+-------------------------------------------------------------------------+
+-------------------------------------------------------------------------+
| CONFERENCE CONFIGURATION RECORD: |
|-------------------------------------------------------------------------|
| Start Stop Length Record Type Description |
|=========================================================================|
| 1 7 7 STRING Name of the conference, upper case. |
|-------------------------------------------------------------------------|
| 8 87 80 STRING Path/name to USERS file. |
|-------------------------------------------------------------------------|
| 88 167 80 STRING Path/name to MESSAGES file. |
|-------------------------------------------------------------------------|
| 168 168 1 STRING Allow ANSI in REPs? "Y" or "N". |
|-------------------------------------------------------------------------|
| 169 169 1 STRING Allow high/low ASCII in REPs? Y, N. |
|-------------------------------------------------------------------------|
| 170 171 2 INTEGER Security level needed to join. |
|-------------------------------------------------------------------------|
| 172 173 2 INTEGER Security level needed to post. |
|-------------------------------------------------------------------------|
| 174 234 61 STRING Tagline for this conference. |
|-------------------------------------------------------------------------|
| 235 235 1 STRING Fido-style tearlines? ("Y" or "N"). |
|-------------------------------------------------------------------------|
| 236 236 1 STRING Fixed-length message base? (Y, N). |
|-------------------------------------------------------------------------|
| 237 334 98 STRING Reserved for future use. |
+-------------------------------------------------------------------------+